|
![](/i/fill.gif) |
I must admit to liking the idea of a POV library... especially a .POV. Being
a software engineer by trade thats not really surprising!
For many of us hard core coders that wouldn't be a bad solution. But it
would require a .NET developement environment and they don't come cheap
(unless your boss provides one like mine does!)
POVRay has always been free and I hope it will remain so. If it suddenly
requires an expensive developement suite like VisualStudio that blows the
whole "free" thing out of the water.
Nice idea, but I doubt it will fly.
Rarius
"Bryan Valencia" <no### [at] way com> wrote in message
news:47040096$1@news.povray.org...
> I've been following the "new language SDL" thread for a while, but I don't
> know if this topic has been covered.
>
> Having been a fan of Borland, and now a user of Visual Studio, I would
> like to present the notion of using a language-independent framework, like
> the .net framework and then document it so well that us users can write
> our own front-end languages, a la Visual Basic, C#, J#, ASP.NET, etc.
>
> So there would be the ".POV Framework" and then C#.POV, J#.POV, Visual
> POV...
>
> Also, if I want to create a post-processor library, or an animation
> utility, or a complicated subroutine that can create a random moon for
> example, then the compiled libraries could work with all the
> implementations.
>
> Maybe (and this is a big maybe) we could boil down the SDL to a set of
> libraries that can be plugged in to Visual Studio, or used with Java or
> Perl, etc.
>
>
>
> I know this is a lot of work, but it would get the POV team out of the
> language biz and let them focus on thing like rendering engines and speed
> optimizations.
>
> Sorry if this has been brought up previously, but I missed it if it was.
Post a reply to this message
|
![](/i/fill.gif) |